A few notes:

• The whitespace is all over the place in your code, looks like a mix of tabs and spaces. Also other clashing coding styles, like no space after keywords etc. Please check https://github.com/sigrokproject/libsigrok/blob/master/HACKING
• There's still lots of debug/TODO stuff in the code, to the point that it seems unfinished. It's fine to submit a driver that doesn't implement everything yet (I'd expect it, with hardware this versatile), but just leave the TODO, dead code etc stuff out. The thing to do is submit finished features, not leave half-finished things in the code.
• I'm not sure I get the dependency on libiio here. What does it bring to the table that you can't do with regular libusb calls, like every other libsigrok USB-using driver? It doesn't look to me like the kernel iio subsystem knows about the adalm2k at all, so what's libiio do for you? I'd like to avoid pulling in a libiio dependency if it's superfluous.

Alright, note taken. I will be updating the code when I have the time.
In regards to libiio, I have no clue how to use libusb calls at this current moment (please let me know if you have any helpful resources to getting started), and it also helps with setting up the device, such as setting up buffer size, sample rate, enable/disable channels, setting up triggers, etc.
Thank you for your feedback!

The libusb docs of course, but most of all check the code in other sigrok drivers. Lots of them use libusb to interface with the hardware.